Wireless backbone and structured wireless

ABSTRACT

Methods, systems, and computer readable media described herein can be operable to provide a 6 GHz backhaul within a premise. Adapters may facilitate a conversion of communications between one or more local area networks and one or more wide area networks. A 6 GHz backhaul may be used by one or more access points to support various wireless services having unique or differing operational and bandwidth requirements. A 6 GHz backhaul may be used to pass communications between an adapter and a network interface device and/or between the adapter and one or more access points.

CROSS REFERENCE TO RELATED APPLICATION

This application is a non-provisional application claiming the benefitof U.S. Provisional Application Ser. No. 62/868,583, entitled “6 GHzWireless,” which was filed on Jun. 28, 2019, and is incorporated hereinby reference in its entirety. Further, this application is anon-provisional application claiming the benefit of U.S. ProvisionalApplication Ser. No. 62/896,608, entitled “6 GHz Wireless,” which wasfiled on Sep. 6, 2019, and is incorporated herein by reference in itsentirety.

TECHNICAL FIELD

This disclosure relates to a wireless backbone and structured wireless.

BACKGROUND

Usage of unlicensed spectrum continues to grow with the growth inwireless devices and services that are available to subscribers. Therise in bandwidth usage, coupled with a lack of new mid-band unlicensedspectrum allocations has created serious congestion issues in availablemid-band unlicensed spectrum.

The 6 GHz band is in a prime area of the midband spectrum. Variousregulations have been implemented to protect established microwavesystems from interference. Regulations also enable microwave systems tobe freely deployed and operated.

Regulations have been approved to allow use of the 6 GHz band byunlicensed devices. The regulations include limitations would requirethat unlicensed devices operate only in locations and frequencies thatwill not create interference for other users of the 6 GHz band. The FCChas considered varying treatment for four sub-bands of the 6 GHz band,wherein the sub-bands include:

U-NII 5: 5925-6425 MHz

U-NII 6: 6425-6525 MHz

U-NII 7: 6525-6825 MHz

U-NII 8: 6875-7125 MHz

Different regulations have been proposed for each of the sub-bands.Example use limitations that may be imposed for the sub-bands include:

-   -   For the U-NII 5 and U-NII 7 sub-bands:        -   i. Unlicensed devices may only be allowed to transmit under            the control of an automated frequency coordination (AFC)            system.        -   ii. The AFC system may identify frequencies on which            unlicensed devices may operate without causing harmful            interference to fixed point-to-point microwave receivers.        -   iii. Unlicensed devices may operate at a standard power            (e.g., 4 W, 1 W, etc.).    -   For all of the 6 GHz sub-bands:        -   i. Unlicensed devices may be restricted to indoor use and            may be required to operate at lower power (e.g., 1 W, 250            milliwatts, 24 milliwatts, etc.), without requiring the            coordination of an AFC system.        -   ii. The frequencies in the U-NII 6 and U-NII8 sub bands are            used for mobile services, such as the Broadcast Auxiliary            Service and Cable Television Relay Service, as well as fixed            satellite services. The itinerant nature of the mobile            services makes the use of an AFC system impractical.        -   iii. The combination of lower power and indoor operations            may protect other registered services already operating on            these frequencies from harmful interference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example network operable to facilitate device managementbased upon a determination of proximity to one or more exclusion zones.

FIG. 2 is a flowchart showing an example process for directing a STA tospecific channel based upon potential operating performance at a 6 GHzchannel.

FIG. 3 is a flowchart showing an example process for scanning for asatisfactory 6 GHz channel.

FIG. 4 is a flowchart showing an example process for establishing atiming distribution between an AP and STA.

FIG. 5 is a flowchart showing an example process for establishing atiming distribution between an AP and STA, wherein the STA determineswhether the AP offers the timing distribution from a certain source at acertain service level.

FIG. 6 is a block diagram showing an example system for transmitting andreceiving signals over a 6 GHz backbone.

FIG. 7 is a block diagram showing an example network architecturefacilitating use of a 6 GHz wireless band.

FIG. 8 shows an example utilization of mmWave to 6 GHz bridging.

FIG. 9 is a block diagram showing an example home network in whichbroadband is brought into a premise using 6 GHz and a 6 GHz adapter.

FIG. 10 is a block diagram showing an example home network that issupported by a 6 GHz backbone.

FIG. 11 shows an example schematic of a mmWave to 6 GHz adapter.

FIG. 12 shows wider connections for higher bandwidth connections andnarrower connection for lower bandwidth connections.

FIG. 13 is a block diagram of a hardware configuration operable tofacilitate and utilize a 6 GHz backbone and/or 6 GHz wirelesscommunications.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

Methods, systems, and computer readable media described herein can beoperable to provide a 6 GHz backhaul within a premise. Adapters mayfacilitate a conversion of communications between one or more local areanetworks and one or more wide area networks. A 6 GHz backhaul may beused by one or more access points to support various wireless serviceshaving unique or differing operational and bandwidth requirements. A 6GHz backhaul may be used to pass communications between an adapter and anetwork interface device and/or between the adapter and one or moreaccess points.

Automated Frequency Coordination (AFC)

FIG. 1 shows an example network 100 operable to facilitate devicemanagement based upon a determination of proximity to one or moreexclusion zones.

In embodiments, operation of a device (e.g., an access device such as anaccess point (AP) 105 and/or one or more stations 110 associated withthe AP 105) may be dependent upon communications with an AFC system 115.An AP 105 as described herein may include a RLAN (radio local areanetwork) device, a WLAN (wireless local area network), and any otherdevice configured to facilitate wireless communications with otherdevices. The AFC system 115 may include a database that containspre-calculated exclusion zone data for one or more microwave paths. Itshould be understood that spectrum availability may be calculated uponrequest. The exclusion zone data may be updated at the databaseperiodically (e.g., hourly, daily, etc.) or in response to an additionor deletion of data associated with a microwave path. Communicationsbetween a device and the AFC system 115 may be over wired or wirelesslinks not in the 6 GHz band. The AFC system 115 and its database may beconnected to a packet-based wide area network (e.g., wide area network(WAN) 120), including but not limited to the Internet. Each of one ormore devices (e.g., AP 105) may register with the database. Initialregistration and query may be made outside of the 6 GHz bands. Inembodiments, each device (e.g., APs 105) may also register devices thatare associated with the device (e.g., STAs (stations) 110, clients,etc.). Each device may query the database with location information(e.g., location information associated with a current location of thedevice), an identification of the device type, identifying information(e.g., unique identifiers), and/or other information associated with thedevice. Based upon the query received from each respective one device,the database may determine a proximity of the respective device to oneor more exclusion zones.

A device (e.g., AP 105) may automatically determine a geographiclocation at which the device is currently positioned and/or a locationat which the device has been installed. For example, GPS, cellulartriangulation, or other systems may be utilized to determine a locationof the device. A device may alternatively or additionally be provedusing location information through a local user interface or remotelythrough a provisioning or status interface.

In embodiments, the device may include an internal GPS through which thedevice may determine its current location. The internal GPS may beutilized by a device that is installed at an outdoor location.

In embodiments, the device may communicate with a detached GPS receiverto determine a current location of the device. For example, the GPSreceiver may be installed at an outdoor location while the device may beinstalled at an indoor location. With the location of the GPS receiverbeing known, the device may determine its own location using one or moreWi-Fi location determination features to map back from the GPSreceiver's location. For example, the device may measure a signalstrength and/or direction component associated with one or more wirelesssignals received at the device, and the measurements may be used toidentify a location of the device relative to the GPS receiver.

A STA (station) 110 (e.g., wireless extender, etc.) may determine itslocation by wirelessly communicating with the device (e.g., AP 105). TheSTA 110 may determine its location relative to the device. For example,the wireless extender may use one or more Wi-Fi location determinationfeatures (e.g., signal strength, direction component associated with oneor more received signals, etc.) to map its location relative to thedevice.

It should be understood that cellular triangulation may be used in placeof GPS. Other satellite-based location determination services may alsobe used in the place of GPS, such as Galileo.

The device (e.g., AP 105) may be manually configured with devicelocation information. In embodiments, a technician (e.g., licensedtechnician or installer) may configure the device with locationinformation once the device has been installed. For example, the devicemay be configured with a trusted certificate, blockchain, or otherinformation to be used to authenticate a location of the device that ismanually provided.

The device (e.g., AP 105) may be provided location information through aprovisioning server or configuration server. In embodiments, aprovisioning server may have information about the address of a customerdeploying the device and may provide that address information to thedevice.

In embodiments, the device (e.g., AP 105), or an upstream device (e.g.,controller of the AFC system 115), may be configured to detect amovement of the device. The device, or upstream device, may beconfigured to determine a current location of the device in response toa triggering event. Triggering events may include, but are not limitedto, the following: reboot of the device, detection of a loss or additionof a STA from which communications are received by the device, andothers. In embodiments, a co-located device (e.g., AP (access point))may determine that another co-located device has moved based upon achange in location that is indicated by one or more Wi-Fi locationdetermination features.

An outdoor GPS-AP may utilize an interlock to prevent it from beingmoved and continuing to operate. Such an interlock could cause the AP toreinitialize its GPS position and contact the AFC when it believes ithas been moved. If the device had used a technician provided location, aphysical interlock may be utilized. For example, if the AP lost powerand had power restored, it could attempt to determine if it had beenmoved by querying other location-specific or at leastlocation-indicating attributes. For example, if it was integrated with acable modem, the cable modem could inform the AP whether or not it hadbeen moved to a new HFC (hybrid fiber-coaxial) feed (new power levels,new CMTS (cable modem termination system) communication information,different cable group, etc.). Other location indications could be: DHCPserver changes, DHCP Gateway changes, new clients/loss of old clients,new overlapping Wi-Fi Basic Service Sets (OBSSs). In embodiments, a 6GHz AP may be collocated with a 5 GHz AP and/or a 2.4 GHz AP. If thosecollocated APs report new neighboring APs, one or more new clients, orthe presence of other new wireless devices, the 6 GHz AP may refuse totransmit until its location is updated by a trusted source.

In embodiments, the AFC system 115 may utilize location information frommultiple sources to verify or otherwise improve the level of confidencein a determined location of a device (e.g., AP 105). For example, theAFC system 115 may correlate location information of a device with GPSdata with a physical address associated with a customer (e.g., anaddress recovered from billing data or subscriber information held at asubscriber information server 125 such as a service provider server orother server storing subscriber or account information).

Location Determination Through RF Scans in 6 GHz Band

A device needing to perform location determination, typically an AP 105,initializes and comes up to scan available frequency bands. An AP mayhave access to 2.4 GHz, 5 GHz, and 6 GHz radios. The AP can scan 2.4, 5and 6 GHz bands for Wi-Fi signals. The SSIDs obtainable from receivedWi-Fi transmissions can contribute to an estimate of the AP's location.The signals of other 6 GHz APs may be detected from a 6 GHz scan or fromanalysis of information about 6 GHz SSIDs included in the 5 GHz or 2.4GHz signals. For example, one or more signals received by an AP 105through a 2.4 GHz or 5 GHz radio may indicate a presence or offering ofa 6 GHz SSID by one or more other APs. A goal of 802.11 standards forthe 6 GHz band is to restrict the amount of beaconing and similaractivities to decrease the percentage of airtime given over tobackground or maintenance activities. An AP with 6 GHz capability mayannounce that capability in its 2.4 and/or 5 GHz transmissions.

The AP 105 can also scan 6 GHz bands for the presence of non-Wi-Fisignals. The signals of fixed wireless or other non-Wi-Fi communicationscan be detected and, potentially, their directions recorded. Utilizingenergy detection, an AP need not be able to demodulate or decode a fixedwireless or other non-Wi-Fi communications signal to detect itspresence. In embodiments, further processing, beyond energy detection,is performed on the received signal spectrum. The characteristics of atleast well-known signals such as fixed microwave signals can be appliedto the received signal spectrum and energy signatures of potentialinterest marked for more processing. For instance, fixed microwavesignals are typically 30 MHz wide and occur in pairs. These signals arealso required to be registered with the FCC. In embodiments, a signalspectrum detected by an AP may be processed locally or sent to acontroller 130 or cloud server for further processing.

If the AP 105 is processing the spectrum locally, it may detect acertain combination of fixed microwave signals. With that information,the AP can consult a database containing 6 GHz registered signal sites.Fixed wireless assigned frequencies may be recorded in a database thatalso includes location information. When combined with the Wi-Fi signalinformation, the location of the AP may be ascertained with greatercertainty or less uncertainty. An AP may develop a location estimatebased on these sources of information, even if a GPS or similar locationdetermination equipment is not available. If the AP sends a collectedsignal spectrum to a controller 130 or cloud server, those entitiessimilarly may consult databases of known 6 GHz entities to develop alocation estimate. Those entities may also consult databases of known2.4 GHz and 5 GHz signal sources. That estimate may be returned to theAP for it to use in communication with an AFC system. Alternatively, thecontroller 130 or cloud server may forward the location estimate withinformation identifying the AP to an AFC. If the AP recognizes Wi-Fisignals within the 6 GHz scan, that information may also be used to aidwith location determination.

As mentioned earlier, additional sources of location information mayinclude client devices such as smart phones that have associated withthe AP's 2.4 or 5 GHz radios as well as GPS receivers or the like. Manysmart phones have built-in GPS receivers and can provide an estimate oftheir current location by combining their GPS signals (if any) withother signals in the Wi-Fi bands and other indications as known in theart. The client devices may have an app installed that facilitatescommunication with the AP and indicates to the AP whether or not theclient device will share its current location estimate. In embodiments,a user of a client device may be presented with an option to share itslocation with its associated AP or not. The AP may request a locationestimate from the client device by communicating with the app.Alternatively, the controller may communicate with the client device'sapp on the AP's behalf to acquire the client's location estimate.

The AP may use an algorithm itself to predict its most likely locationbased on the various inputs it received, or it may contact anotherdevice or server, provide the information and receive an estimatedlocation with an estimated location error. An AP or a location servermay use standard techniques of localization and triangulation to predictthe AP's location from the gathered data.

The AFC database (at the AFC system 115) may utilize a buffer tocompensate for potential inaccuracies with respect to the locationinformation carried by a query. The AFC database may identify one ormore frequencies available to the respective device (e.g., AP 105),wherein the available frequencies are based upon the determination ofwhether the respective device is located within an exclusion zone.Further, the database may identify one or more operating requirements,such as transmit power level, based upon the determination of whetherthe respective device is located within an exclusion zone. The databasemay send a list of the available frequencies to the respective device,and the respective device may begin operating according to any operatingrequirements at an available frequency identified from the list.

In embodiments, a device registered with the AFC database may sendheartbeat messages to the database in order to ensure that exclusionzone data is current and to confirm that the device is active. A devicemay deregister from the AFC database when a determination is made thatthe device has been moved by more than a threshold distance (e.g., 50 m,100 m, etc.), when a heartbeat message is not received for longer than acertain duration (e.g., 24 hours, etc.), or in response to anothertriggering event.

If an AP is providing high reliability services, the AP may registerwith more than one AFC and retain records for the at least two differentAFC responses providing channel availability and power levels. The APmay choose to use one AFC's response over another AFC's response if theresponses differ, or it may choose to comply with the union of the tworesponses.

A monitoring site already in position for CBRS may be enhanced to alsocollect signatures of radio traffic in various bands outside the CBRSband. It had been true that radios were fairly dedicated to specificfrequency ranges, but as software defined radios (SDR) with flexiblefront ends have improved in performance and cost-effectiveness, thatlimitation is less accurate. If an SDR is being used for reception only,some of the concerns that attach to SDR are mitigated. One commonconcern is that the filtering for out-of-band emissions for SDRtransmitters is difficult or expensive. If the SDR is only operating asa receiver, that concern is minimized.

6 GHz devices may also include 2.4 GHz and/or 5 GHz radios. This allowsan AP, for example, to provide only minimal beaconing in its 6 GHzallotted channel because its 5 GHz beacon can include information aboutany 6 GHz interfaces. For example, the AP may advertise a 6 GHz SSIDthrough a beacon provided by a 2.4 or 5 GHz radio of the AP.

If a 6 GHz device, such as an AP or mesh station, does not include anLTE radio, one or more of its clients or associated devices may, such asa cell phone. In that case, an AP, for example, might ask its clientsfor information about networks seen over the air, even if it does notrequest an actual location determination from those devices.

The AFC database may alternatively receive information such as 5 and 6GHz signals received by the device seeking to register. The informationabout 5 and 6 GHz signals received may include SSIDs from Wi-Fi APs, aswell as frequencies where energy was detected above a threshold in the 5and 6 GHz bands. The information about 5 and 6 GHz signals received mayinclude signal strengths associated with the received signals as well asangular directions.

The database may correlate received energy signatures with known 6 GHzfixed microwave deployments to determine a device's probable location.Known 6 GHz microwave deployments may be registered with their frequencyusage and locations. Detection of a certain pattern of 6 GHz signals canbe matched against known deployments to allow the AFC database toestimate where a device would have to be to receive that pattern of 6GHz signals. For example, fixed microwave links in the 6 GHz band areknown to be 30 MHz wide and to exist in pairs. The database wouldconsider not only the detected 6 GHz signal in making a frequencyassignment for a requesting device that reports receiving at least one30 MHz signal in its 6 GHz scan. Detection of one 30 MHz wide signalnecessarily implies that the matching paired signal may also potentiallybe affected if the device begins transmissions in the frequenciesassigned to the paired signal.

Similarly, the database may correlate the received SSIDs with known SSIDlocations to determine a device's probable location. The database maycombine the various estimations to form an estimate with greaterconfidence. If the estimates formed based on different informationsources do not indicate the same location within a certain amount ofuncertainty, then the database may choose which estimates to rely uponto make a registration decision, or it may reject the registrationrequest entirely. The relative signal strengths and directions may becombined with the location estimation to determine if the informationprovided is credible.

The database may also use the relative signal strengths and directionsto determine the transmit power level allowed for a device as well as anallowed frequency block. For example, a device that reports very lowsignal levels for 5 and 6 GHz received signals may be within a buildingso that those other signals reach it only faintly. In this case, thedatabase could allow that device to use a higher transmit power safelybecause its transmissions will also be attenuated heavily before theyreach any 6 GHz fixed microwave operations.

Location Awareness

The device, or a related upstream device, may be configured to determinethat the device has moved by comparing a current location of the deviceto a baseline location of the device (e.g., the location informationautomatically determined or manually entered during an install orinitial setup of the device). Additional description for comparing acurrent location of a device to a baseline location of the device todetermine that the device has been moved may be found within U.S.application Ser. No. 15/131,693, entitled “Detecting Device Movementthrough Electronic Fingerprint Analysis,” filed on Apr. 18, 2016. Thedisclosure provided by U.S. application Ser. No. 15/131,693 isincorporated herein. The device may respond to a determination that acurrent location of the device differs from the baseline location of thedevice by initiating an action for ensuring compliance with regulatoryrequirements. The device may be configured to initiate an action forensuring compliance with regulatory requirements only when thedifference between the current location of the device and the baselinelocation of the device exceeds a certain threshold. Actions for ensuringcompliance with regulatory requirements may include, but are not limitedto, the following: halting AFC-regulated operation; reducing transmitpower; changing channel to a channel that does not require AFC-regulatedoperation; powering down the device; and others.

In embodiments, access may be gained to a database of AP SSIDs linkedwith locations. Such a database may be offered as a service where adevice can survey the APs that it can hear and ask the database wherethe device is most likely physically located based upon a report of whatit can hear.

An AFC may offer similar services using a wider network of networks. AnAFC may use data from its own sensors to gather information aboutlocations. An AFC's own sensors' locations may be well known, allowinginformation from sensors with well-known locations and well-knownantenna patterns to be trustworthy. An AFC may accept information fromdevices already having trustworthy accepted locations about 6 GHzsignals, Wi-Fi APs (SSIDs and RSSI) and/or LTE or 5G base stations ormicrocells. Also available in some areas and from certain devices orsensors could be 900 MHz signals for Wi-Fi HaLow, Lora, SigFox or othersuch signals. The AFC may use that information, when the device istrusted, to enhance its mapping ability. It may also doublechecklocation information from new devices seeking authorization byrequesting information from that untrusted device about other signals ithas detected. If the other information matches to within a certaindegree of error the location information provided by the new device,then the AFC would have additional confidence that its reported locationis correct. On the other hand, if the location information from thedevice does not agree with the wireless environmental informationprovided by that device, then the AFC may not choose to trust thatdevice or provide it with a high power channel authorization.

Alternatively, a device might use an available service to determine itslocation in lieu of having the ability to determine its location throughaccess to a GPS or through the use of cellular location services. Whenthe device reports its location to an AFC, it may provide a margin oferror for that determination based on a factor returned by the locationservice.

Database Management

A controller or database may be utilized to store exclusion zone dataassociated with areas in which unlicensed band usage may impactmicrowave paths. The controller or database may include or may be a partof the AFC system. Updates to exclusion zone data may be pushed to thecontroller or database or may be pulled by the controller or databasefrom one or more sources of exclusion zone data. Exclusion zone data mayinclude one or more geographic locators (e.g., GPS coordinates, etc.)making up boundaries of exclusion zones or that are otherwise positionedwithin boundaries of exclusion zones. Exclusion zones may be areas thathave been designated as areas in which unlicensed band usage may impactmicrowave paths.

In embodiments, periodically or in response to certain triggers, thecontroller or database may identify one or more devices that areoperating at a location that falls within a region that is the subjectof an update which has been made to the exclusion zone data. Forexample, when an update to exclusion zone data is received, thecontroller or database may check location information associated withone or more devices to determine whether the location information of anyof the one or more devices indicates that the device is located withinan area that is affected by the update. As another example, thecontroller or database may periodically (e.g., hourly, daily, weekly,etc.) determine whether the location information of any of the one ormore devices indicates that the device is located in an area that isaffected by an update made to the exclusion zone data during the certainduration covered by the period. In response to a determination that adevice is located within an area that is affected by an update to theexclusion zone data, the controller or database may output updatedfrequency information (e.g., AFC operational requirements) to thedevice.

In embodiments, the controller or database may include channel scanningfunctionality or secure and authenticated access to external channelscanning functionality.

In embodiments, the controller or database may maintain a schedule ofband usage by one or more microwave systems. The controller or databasemay clear or terminate channel usage at one or more devices based uponthe schedule.

In embodiments, the controller or database may generate a schedule ofband usage by one or more microwave systems. The controller or databasemay monitor channel usage by the one or more microwave systems and mayrecord times/days during which the microwave systems are active. Basedupon the monitored channel usage, the controller or database maygenerate a schedule of daily/weekly/yearly use. The controller ordatabase may clear or terminate channel usage at one or more devicesbased upon the schedule.

In embodiments, the controller or database may direct one or moredevices (e.g., one or more devices within an MDU (multiple dwellingunit), campus, etc.) to use certain frequencies based upon frequenciesused by other devices. The controller may also direct other devices toalter their power levels or to use directed null forming to avoidcausing interference. For example, the controller or database mayallocate 6 GHz channels among a group of APs that are within a certainproximity of each other, wherein the allocations are made on anon-interference basis.

In embodiments, a device (e.g., an AP) may receive communicationsindicating that a microwave path with which the device has beenassociated based upon a current location of the device has become activeor inactive. For example, a beacon positioned in close proximity to amicrowave system may determine a current state of the microwave system.When the state of the microwave system changes (e.g., when thecorresponding microwave path becomes active/inactive), the beacon mayoutput notifications indicating the state change to one or more devicesthat are located within an exclusion zone associated with the microwavepath. For example, the notifications may include clearances ortermination requests that notify the one or more devices that one ormore frequencies have become available or unavailable. Further, thenotifications may notify the one or more devices that operationalrequirements either may be temporarily ignored or should be adhered tobased upon the identified state change.

In embodiments, an AP may scan a channel to determine whether a 6 GHzband is available. For example, an AP operating at low power may carryout a scanning of the 6 GHz band as a background operation. If signalsare detected on the 6 GHz band, the AP may refrain from using the 6 GHzband or may alternatively remain at low power until the 6 GHz band isclear.

Operational Deployment

In embodiments, an AP may have both a 6 GHz radio and another radio(e.g., 2.4 or 5 GHz radio). If a 6 GHz AP has a legacy band (2.4 or 5GHz) and a 6 GHz STA also has legacy capabilities, then the AP mayadvertise in the legacy band its 6 GHz capabilities. In embodiments, adevice may be configured with a 2+5+6 solution. In embodiments, a devicemay be configured with a 2+5+5/6, wherein one of the radio chains isswitchable between 5 GHz and 6 GHz.

If the units are a bookend solution and/or controlled by a homenetworking controller, a home networking controller may direct aSTA/extender to a specific 5 or 6 GHz channel depending upon the STA's 5GHz RSSI. The controller may consider the performance of similarstations already attached at 6 GHz to determine whether or not the STAshould be directed to the higher band. If the higher channel has a verywide channel with little or no interference, then the controller maychoose to move the STA.

FIG. 2 is a flowchart showing an example process 200 for directing a STAto specific channel based upon potential operating performance at a 6GHz channel. For the controller to make good decisions, it needs accessto the AP's AFC channel/power assignments. The APs might handle therequest process independently and keep the controller up to date on anyassignments or refusals. As the controller decides which band to assigna station to, the controller may consider the STA's current RSSI as wellas RSSI history, as well as the channel assignments and power levellimits of the APs it controls. At 205, the controller may determine a 5GHz RSSI of a STA. At 210, the controller may determine a breadth andlevel of interference of a 6 GHz channel. At 215, the controller maydetermine whether the 6 GHz channel may offer better performance for theSTA than the currently used 5 GHz channel. If the determination is madethat the 6 GHz channel does not offer better performance for the STA,the controller may direct the STA to the 5 GHz channel at 220. If thedetermination is made that the 6 GHz channel does offer betterperformance for the STA, the controller may direct the STA to the 6 GHzchannel at 225.

FIG. 3 is a flowchart showing an example process 300 for scanning for asatisfactory 6 GHz channel. If the units are un-related, a STA may turnon and activate its 5 GHz radio and perform normal scanning at 305. If a6 GHz advertisement is not found at 310, the STA may stay at the 5 GHzband at 315. If an AP is found that also advertises a 6 GHz capabilityat 310, the STA can consider which 6 GHz channel/band is included in theAP's information. For example, the STA may determine operationalrequirements associated with the 6 GHz band at 320. Since the US currentregulatory proposals indicate that the power level may be set bychannel, the STA may take that into consideration. If the determinationis made at 325 that the operational requirements of the 6 GHz band aresatisfactory to the STA, the STA may activate a 6 GHz radio at 330. If,at 325, the STA determines that the operational requirements of the 6GHz band are not satisfactory, the STA may continue scanning at 335. Forexample, if the channel is a low power channel, the STA maypreferentially keep looking until it finds an AFC/high power channel.

In embodiments, multiple APs may coordinate to maximize efficiency ofband usage between the multiple APs. For example, the APs may coordinateuse of the large bands based upon the varying regulatory requirementsassociated with each of the bands.

With the potentially lower power limits (at least for a while),spreading STAs across multiple APs may be helpful to use the widebandwidth to bring up the data rate. A deployment constrained to a lowpower level, such as 250 mW, may require more APs to cover the same areacompared to a standard 5 GHz AP (1 W).

A collection of APs that are centrally coordinated can send in separateAFC requests and a central coordinator might choose how to distributethe STAs based on the responses. In embodiments, a controller may directan AP to resend its request if the results are not acceptable.

STAs may be directed to go from standard power to low power or toevacuate the band if an AFC withdraws the previously allowed channel(s)from an active AP.

In embodiments, an AFC may withdraw a channel allocation at any time. Ifan AP receives a withdrawal notice from the AFC, the AP may notify allSTAs that they must at least drop to low power. If the operationalparameters do not allow the STAs to change their power level and remainon the channel, then the AP may direct the STAs to shift to a non-6 GHzband until the AP can obtain a new assignment from the AFC.

Timing Distribution/Low Latency Services/QoS

PTP (IEEE-1588) allows distribution of timing over Ethernet. DTP (DOCSISTiming Protocol) from CableLabs extended this technology over DOCSIS.

Motivation for 6 GHz Wi-Fi application: new unlicensed frequency bandlikely to have little interference for a while, especially if all fourbands are opened. If only band 6 is open, that advantage will beshort-lived.

This disclosure applies to a cable modem GW that also has Wi-Fiincluding 6 GHz (but not required). The CM supports DTP as does itssupporting CMTS. The CMTS/CM could provide several different timingsources. As different mobile providers advance their networks from 4G to5G at different rates, there may be different timing feeds available fordifferent small cell/pico cell uses. The timing feeds may also be ofdifferent qualities (4G vs 5G 1 ms).

The AP can advertise its support for timing distribution or provide itlater in a capabilities exchange. This notification could come via afield in the beacon or in a capabilities exchange after the STAs areassociated. The notification could include multiple possible timingsources that the CM/AP may have available. The notification could alsoindicate the accuracy or quality of each potential timing source. A STAdecides whether an AP can provide a timing feed that it needs. The STAcan request the timing feed. If a STA wants to receive a timingdistribution, it notifies the AP that that it wants to receive a timingdistribution. That notification could indicate which timing source theSTA is interested in and/or potentially a level of accuracy or qualitythat it needs to receive. The AP may evaluate whether it can provide theservice that the STA has requested. The AP may need to communicate withthe CM and/or the CMTS to ensure that the requested service and QoSlevel can be provided. The AP/CM passes that request back to the CMTS.If the CM/AP has to support multiple timing feeds then the CM may selectwhich one to use for its internal systems, or it may not use anyspecific feed directly. If the AP can provide the STA with the serviceit requested, then it selects an OFDM/OFDMA downstream and upstreamchannel to carry the timing messages. For example, the timing messagesmay be carried over a selected 6 GHz channel. Note that the channel mayactually be one or more resource units (RU) as known in 11ax withlimited bandwidth, but that can be dedicated to this purpose. The AP andSTA begin communicating over that RU according to a schedule developedby the AP to accommodate the QoS requirements of the service level thatthe STA had requested. The AP may choose a limited set of MCS settingsfor the channel to ensure predictability and good performance.

FIG. 4 is a flowchart showing an example process 400 for establishing atiming distribution between an AP and STA. At 405, the AP may output anadvertisement for support of timing distribution. At 44, the AP mayreceive a request from a STA to receive a timing feed, wherein therequest is output from the STA in response to the STA recognizing theadvertisement. At 415, a channel may be selected for carrying the timingmessages. For example, the timing messages may be carried over aselected 6 GHz channel. At 420, a schedule for communicating the timingmessages may be developed based upon a service level indicated by therequest that is received from the STA. At 425, communications may beinitiated between the AP and the STA over the selected channel accordingto the developed schedule.

FIG. 5 is a flowchart showing an example process 500 for establishing atiming distribution between an AP and STA, wherein the STA determineswhether the AP offers the timing distribution from a certain source at acertain service level. At 505, a STA may receive, from an AP, anadvertisement message carrying information associated with timingdistribution that is offered by the AP. At 510, the STA may identifysources and/or service levels offered by the AP. At 515, the STA maydetermine whether a required timing service is offered by the AP. If therequired timing service is not offered by the AP, the STA may evaluateother methods for receiving a timing distribution at 520. If therequired timing service is offered by the AP, the STA may output arequest to receive a timing feed from a specified source at a specifiedservice level at 525. At 530, communications may be initiated betweenthe AP and STA to receive the requested timing feed.

6 GHz Backbone

In embodiments, the 6 GHz band may be utilized by a collection of accesspoints or extenders as a backbone to support a wireless network that isprovided to one or more STAs or clients. One or more channel blockswithin one or more sub-bands of the 6 GHz band may be allocated to eachof collection of APs or extenders of a wireless network.

FIG. 6 is a block diagram showing an example system for transmitting andreceiving signals over a 6 GHz backbone 605. In embodiments, two logicalinterfaces may be provided over a single 6 GHz radio 610 (e.g., LAN SSIDand WAN SSID). Traffic between the WAN and LAN SSIDs may go through arouter 615 for typical WAN ingress functions (e.g., firewall). Inembodiments, a VLAN tag may be used to distinguish and separate WAN andLAN traffic. One or more extenders 620 may associate to the LAN SSID andmay acquire an IP address from a gateway (e.g., the router 615 may beintegrated within a gateway device). For example, the one or moreextenders 620 may communicate through the LAN interface 625. Theextender(s) 620 may be a Wi-Fi client. The WAN device 630 may discoverand associate with a gateway. The WAN device 630 may be a Wi-Fi client.Upon association, a link-up event occurs on the gateway. The gatewayacquires an IP address from the WAN network. The WAN device 630 has afixed, well-known IP address for management.

In embodiments, each respective channel block of one or more channelswithin the 6 GHz band may be allocated to a certain room or space withina premise. For example, a room configured with virtual reality headsetsmay have its in-room extender (e.g., an extender 620) configured with a160 MHz channel block while another room with only cell phones andlaptop users may only have an 80 MHz channel block configured. Powerlevels may be optimized for each channel based upon one or more factorsassociated with the location and/or barriers between each room or spaceand a 6 GHz AP or extender. A separate channel block allocation may beused for communication between the in-room extenders and an AP (e.g.,gateway).

In embodiments, signals may be received at and transmitted from asubscriber premise through a network interface device (NID). A 6 GHzbackbone may be used to pass signals between the NID and an AP that ispositioned within the premise (e.g., the AP may be centrally locatedwithin the premise). The 6 GHz backbone may be provided by the NIDitself, or by a separate device that is either attached to the NID,wall-mounted near the NID, or otherwise positioned near in proximity tothe NID. For example, home network wiring may be eliminated by adding a6 GHz radio to the NID and using one or more 6 GHz network extenders toprovide Wi-Fi coverage throughout the home.

A network may be configured to use a standard power backbone lineoffering higher throughput in a certain size channel versus thethroughput available for a low power backbone. For example, a NID to APbackbone that may also allow extenders to join may use a 320 MHz channelblock at standard power to pass information between the NID and the APsand extenders. Within each room, the extenders may use low powertransmissions over 160 or 320 MHz channel blocks. Even though thesechannels may be as large or larger than the backbone link, the lowerpower will result in lower throughput within the rooms. This is stilladvantageous because it allows the in-room extenders to be less likelyto interfere with each other while still providing plenty of bandwidthfor the devices in the room to provide wireless services.

Each in-room extender also has the option of using 2.4 or 5 GHztransmission bands as well as the 6 GHz transmission band. If anextender has client devices that require the lower bands, the extendermay have additional Wi-Fi radios, such as 2.4 or 5 GHz radios, tosupport those legacy devices. The traffic to and from the in-roomextender would still be carried over the 6 GHz backbone. In embodiments,the one or more extenders 620 may communicate through a LAN interface640 via an Ethernet port 645, a LAN interface 650 via a 2.4 GHz radio655, and/or a LAN interface 660 via a 5 GHz radio 665.

In embodiments, the one or more network extenders 620 may be configuredto communicate with the WAN device 630 via the 6 GHz backbone 605. Forexample, communications may be received from and forwarded to one ormore extenders 620 via the LAN interface 625, and communications may bereceived from and forwarded to the WAN device 630 via the WAN interface635.

FIG. 7 is a block diagram showing an example network architecturefacilitating use of a 6 GHz wireless band. In embodiments, an adaptermay be located in a premise, wherein the adapter converts WANcommunications to Wi-Fi signals, which are then communicated to one ormore devices over a 6 GHz wireless band. In embodiments, one or more WANadapters (e.g., 5G mmWave to 6 GHz adapter 705, LTE to 6 GHz adapter710, PON to 6 GHz adapter 715, and/or HFC to 6 GHz adapter 720) mayfacilitate signal translations to support communications between a 6 GHzWAN and one or more various communication networks (e.g., 5 GHz/LTE 725,PON 730, HFC 735). A PON to 6 GHz adapter 715 may be connected to an ONT740. Each WAN adapter may include a 6 GHz radio to transmit and receive6 GHz wireless signals to and from a gateway device (e.g., tri-bandgateway 745). A tri-band gateway 745 may include a 2.4 GHz radio, a 5GHz radio, and/or a 6 GHz radio, and the gateway may facilitatecommunications between the 6 GHz WAN and one or more WLANs (e.g., 5 GHzWLAN and/or 6 GHz WLAN). The gateway may communicate with one or moreextenders (e.g., 6 GHz extender(s) 750 and/or 5 GHz extender(s) 755),client devices 760, and/or mobile device(s) 765 over the one or moreWLANs.

FIG. 8 shows an example utilization of mmWave to 6 GHz bridging. Inembodiments, an adapter 805 may be installed at a premise 810 (e.g., theadapter 805 may be installed at a window 815 of an exterior wall 820 ofthe premise 810), and the adapter 805 may operate as a mmWave to 6 GHzconvertor. The adapter 805 may include a 5G UE to 6 GHz Wi-Fi solution,thereby providing a 6 GHz WLAN within the premise 810. A 4×4 6 GHzsolution may be used to connect to a gateway 825. The adapter 805 mayprovide a 6 GHz backhaul, and the gateway 825 may have tri-bandcapability, thereby facilitating communications between the gateway 825and the adapter 805.

In embodiments, the adapter 805 may include a removable interface module(e.g., removable interface module 1130 of FIG. 11 ), the removableinterface module facilitating a conversion of mmWave communications to 6GHz communications and vice versa. The removable interface module may beinstalled at either the gateway device 825 or the adapter 805, and theremovable interface module may be moved between the gateway device 825and the adapter 805 based upon the quality of connection to an RCU 830providing mmWave communications.

In embodiments, a user or installer may verify the performance of a 6GHz backhaul when the removable interface module is installed at thegateway 825 and/or when the removable interface module is installed atthe adapter 805. Based on the performance metrics, the user or installermay install the removable interface module at the device or locationhaving the better or more desirable performance metrics.

In embodiments, the gateway 825 may be configured with multipleoperating modes, wherein the gateway 825 operates in a first mode whenan installation of the removable interface module at the gateway 825 isdetected and a second mode when an installation of the removableinterface module at the gateway 825 is not detected. For example, whenoperating in the first mode, the gateway 825 may disable a 6 GHz modulethat is used by the gateway 825 to communicate over a 6 GHz backhaulprovided by the adapter 805. When operating in the second mode, thegateway 825 may enable the 6 GHz module that is used to communicate overthe 6 GHz backhaul provided by the adapter 805.

FIG. 9 is a block diagram showing an example home network in whichbroadband is brought into a premise 905 using 6 GHz and a 6 GHz adapter910. In embodiments, the adapter 910 may be connected to an ONT 915 viaa wired connection (e.g., 2.5 GigE). The adapter 910 may include a 6 GHzradio through which a 6 GHz wireless backhaul may be provided. Theadapter 910 may be installed within the premise 905 in close proximityto the ONT 915. A gateway 920 having a 6 GHz radio may utilize the 6 GHzwireless backhaul that is provided by the adapter 910. With a wirelessbackhaul, the gateway 920 may be placed in an optimal location withinthe premise 905 to provide a wider coverage area within the premise 905.For example, the gateway 920 may be placed at a central location withinthe premise.

In embodiments, the gateway may provide a WLAN that may be accessed byone or more extenders 925 and/or one or more client devices 930. Thegateway 920 may provide one or more services to one or more MoCA clients935 via a wired connection to the MoCA clients 935.

In embodiments, a ceiling mounted AP 940 may be installed at a ceilingof the premise 905. The ceiling mounted AP 940 may be installed at alocation that has access to power but that has no access to a datainterface. The ceiling mounted AP 940 may communicate over the 6 GHzbackhaul provided by the adapter 910 and may provide wireless servicesto one or more client devices 930. The ceiling mounted AP 940 maywirelessly communicate with the gateway 920.

FIG. 10 is a block diagram showing an example home network that issupported by a 6 GHz backbone. In embodiments, a 6 GHz wireless backhaulmay be provided by an adapter 1005 that is located outside of a premise1010 and that is connected to an ONT 1015 via a wired connection. The 6GHz wireless backhaul may be utilized by a gateway 1020 located withinthe premise 1010, and the gateway 1020 may provide wireless services toone or more extenders 1025 and/or one or more client devices 1030 viaone or more wireless interfaces/radios.

FIG. 11 shows an example schematic of a mmWave to 6 GHz adapter. Inembodiments, the adapter may convert signals received through the sub6interface 1105 and/or mmWave interface 1110 to signals that arecommunicated through the 6 GHz interface 1115 and/or Ethernet interface1120. The adapter may provide 6 GHz wireless services and/or Ethernetcommunications to a subscriber premise. In embodiments, the sub6 and/ormmWave RF interfaces and the modem 1125 may be installed at the adapteras a removable interface module 1130, and the removable interface module1130 may be moved from the adapter to a gateway that is located at adifferent location of the subscriber premise.

The adapter may include a SoC (system-on-chip) 1135, DDR 1140, flash1145, LEDs 1150, and/or buttons 1155.

In embodiments, the 6 GHz interface module may include a plurality ofantennas and may support multiple input-multiple output (MIMO) services(e.g., 2×2, 4×4, etc.).

6 GHz Structured Wi-Fi in the Home or SMB

Wi-Fi services have been deployed in the home, and small to mediumbusinesses (SMB), largely on an ad hoc basis. Even as more sophisticatedmesh schemes have been used to extend coverage, the channels and bandsused have been restricted to the 2.4 GHz and 5 GHz bands which arerelatively congested. The power levels in those bands are such that evenin detached single family residences (SFR) there is enough leakage fromone home to another that few residences do not have impinging signalsfrom other nearby residences. In the case of multiple dwelling units(MDU) and SMB units, the situation is even worse with most businesseshave multiple overlapping signals from other Wi-Fi APs and theirclients.

The 6 GHz band may offer improved conditions with an approach referredto herein as structured Wi-Fi. The 6 GHz band may offer several hundredGHz of open channels, with the potential restriction that the powerlevels allowed may be quite low (250 mW to 100 mW). Structured APs mayoffer 6 GHz as well as 2.4 and 5 GHz services. The APs may provide morecomplex switching and routing for packets than are currently common.

A backbone AP may connect using a wide 6 GHz channel to at least oneother backbone AP. The backbone APs may operate as a mesh to minimizethe number of wireless hops that a packet must traverse to reach a WANconnection. Subtending from the backbone APs' mesh are local APs andtheir clients. FIG. 12 is a block diagram showing an example networkcomprising a plurality of backbone APs.

FIG. 12 shows wider connections for higher bandwidth connections andnarrower connection for lower bandwidth connections. For example, theconnections between the WAN 1205 and the backbone APs 1210, theconnections between the backbone APs 1210, and the connections betweenthe backbone APs 1210 and the extenders 1215 may be higher bandwidthconnections than the connections between the local APs 1220 and/orextenders 1215 and the client devices 1225.

The system uses wider channels, for example 400 MHz channels, for backbone connections, and narrower channels, such as 160 MHz channels, forconnections to clients 1225. A client may associate with a local AP orwith an extender AP, but the backbone connections are separate channelsfrom the client connections. A channel used for client connections couldbe at a lower power as well as using a more narrow channel bandwidth.Lower power signals have more difficulty penetrating walls, so theclient connections to local APs can still provide high speed connectionswithin a room, while not contributing to congestion or causinginterferences with other non-Wi-Fi communications.

In embodiments, an AP may detect the usage of one or more 6 GHz channelsby one or more neighboring APs. For example, in an MDU, an AP may beconfigured to exchange information with neighboring APs, wherein theinformation identifies the channel(s) being used by the APs and/or usemetrics associated with the APs use of the identified channel(s). Basedupon the exchanged information, the AP may determine an optimal 6 GHzchannel to use. For example, the AP may select a 6 GHz channel that isidentified as having the lowest usage level by neighboring APs.

In embodiments, an AP may change 6 GHz channels until a channel is foundthat is not being used by a neighboring AP.

In embodiments, the information exchanged between neighboring APs maytrigger a reallocation of the channels used by each AP. For example,each of the neighboring APs may be assigned to a unique channel.

Physical Instantiations

The combination backbone AP/Local AP (e.g., the integrated backbone AP1210 and local AP 1220 shown in FIG. 12 ) may be in a standard blackrectangular box, but there are advantages to placing these APs atceiling level. For example, a combined backbone AP and local AP may beintegrated in a ceiling mounted AP 940 of FIG. 9 ). There are fewerobstacles high in the room and fewer moving obstacles that can cause asignal level to change often. One possible instantiation is in a ceilingfan. These fans typically have substantial heft compared to a simplelight fixture making it easier to add the AP circuitry. Fans are alsotypically located in the center of a room making the coverage within theroom easier. A ceiling AP may have one 6 GHz backbone radio that maysupport a wider channel and/or a higher power level than a second radioin the ceiling AP. The second radio may be another 6 GHz radio operatingat a different lower power level and a different channel than thebackbone AP. The second radio may be a standard single or dual band 2.4or 5 GHz Wi-Fi radio. The second radio may be a 6 GHz Wi-Fi radio or aLiFi radio. Either of the last two options are also good for keepingsignals within a room and minimizing interference with adjacent rooms.

In embodiments, the ceiling mounted AP may be installed at a locationthat is powered but that does not have a wired data connection. Forexample, the ceiling mounted AP may be installed at a ceiling fan orother ceiling mounted fixture having access to power. The ceilingmounted AP may connect to a wireless backhaul (e.g., a 6 GHz wirelessbackhaul) to provide wireless services to one or more client devices viaone or more interfaces (e.g., 2.4 GHz, 5 GHz, 6 GHz interface, etc.).

Timing Distribution/Low Latency Services/QoS

PTP (IEEE-1588) allows distribution of timing over Ethernet. DTP fromCableLabs extended this technology over DOCSIS.

Motivation for 6 GHz Wi-Fi application: new unlicensed frequency bandlikely to have little interference for a while, especially if all fourbands are opened. If only band 6 is open, that advantage will beshort-lived.

This disclosure applies to a cable modem GW that also has Wi-Fiincluding 6 GHz (but not required). The CM supports DTP as does itssupporting CMTS. The CMTS/CM could provide several different timingsources. As different mobile providers advance their networks from 4G to5G at different rates, there may be different timing feeds available fordifferent small cell/pico cell uses. The timing feeds may also be ofdifferent qualities (4G vs 5G 1 ms).

The AP can advertise its support for timing distribution or provide itlater in a capabilities exchange. This notification could come via afield in the beacon or in a capabilities exchange after the STAs areassociated. The notification could include multiple possible timingsources that the CM/AP may have available. The notification could alsoindicate the accuracy or quality of each potential timing source. A STAdecides whether an AP can provide a timing feed that it needs. The STAcan request the timing feed. If a STA wants to receive a timingdistribution, it notifies the AP that that it wants to receive a timingdistribution. That notification could indicate which timing source theSTA is interested in and/or potentially a level of accuracy or qualitythat it needs to receive. The AP may evaluate whether it can provide theservice that the STA has requested. The AP may need to communicate withthe CM and/or the CMTS to ensure that the requested service and QoSlevel can be provided. The AP/CM passes that request back to the CMTS.If the CM/AP has to support multiple timing feeds then the CM may selectwhich one to use for its internal systems, or it may not use anyspecific feed directly. If the AP can provide the STA with the serviceit requested, then it selects an OFDM/OFDMA downstream and upstreamchannel to carry the timing messages. For example, the timing messagesmay be carried over a selected 6 GHz channel. Note that the channel mayactually be one or more resource units (RU) as known in 11ax withlimited bandwidth, but that can be dedicated to this purpose. The AP andSTA begin communicating over that RU according to a schedule developedby the AP to accommodate the QoS requirements of the service level thatthe STA had requested. The AP may choose a limited set of MCS settingsfor the channel to ensure predictability and good performance.

FIG. 13 is a block diagram of a hardware configuration 1300 operable tofacilitate and utilize a 6 GHz backbone and/or 6 GHz wirelesscommunications. The hardware configuration 1300 can include a processor1310, a memory 1320, a storage device 1330, and an input/output device1340. Each of the components 1310, 1320, 1330, and 1340 can, forexample, be interconnected using a system bus 1350. The processor 1310can be capable of processing instructions for execution within thehardware configuration 1300. In one implementation, the processor 1310can be a single-threaded processor. In another implementation, theprocessor 1310 can be a multi-threaded processor. The processor 1310 canbe capable of processing instructions stored in the memory 1320 or onthe storage device 1330.

The memory 1320 can store information within the hardware configuration1300. In one implementation, the memory 1320 can be a computer-readablemedium. In one implementation, the memory 1320 can be a volatile memoryunit. In another implementation, the memory 1320 can be a non-volatilememory unit.

In some implementations, the storage device 1330 can be capable ofproviding mass storage for the hardware configuration 1300. In oneimplementation, the storage device 1330 can be a computer-readablemedium. In various different implementations, the storage device 1330can, for example, include a hard disk device, an optical disk device,flash memory or some other large capacity storage device. In otherimplementations, the storage device 1330 can be a device external to thehardware configuration 1300.

The input/output device 1340 provides input/output operations for thehardware configuration 1300. In one implementation, the input/outputdevice 1340 can include one or more of a network interface device (e.g.,an Ethernet card), a serial communication device (e.g., an RS-232 port),one or more universal serial bus (USB) interfaces (e.g., a USB 2.0port), one or more wireless interface devices (e.g., an 802.11 card),and/or one or more interfaces for outputting video and/or data servicesto a client device (e.g., television, STB, computer, mobile device,tablet, etc.) or display device associated with a client device. Inanother implementation, the input/output device can include driverdevices configured to send communications to, and receive communicationsfrom one or more networks.

The subject matter of this disclosure, and components thereof, can berealized by instructions that upon execution cause one or moreprocessing devices to carry out the processes and functions describedabove. Such instructions can, for example, comprise interpretedinstructions, such as script instructions, e.g., JavaScript orECMAScript instructions, or executable code, or other instructionsstored in a computer readable medium.

Implementations of the subject matter and the functional operationsdescribed in this specification can be provided in digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them. Embodiments ofthe subject matter described in this specification can be implemented asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a tangible program carrier forexecution by, or to control the operation of, data processing apparatus.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, or declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment. A computer program does notnecessarily correspond to a file in a file system. A program can bestored in a portion of a file that holds other programs or data (e.g.,one or more scripts stored in a markup language document), in a singlefile dedicated to the program in question, or in multiple coordinatedfiles (e.g., files that store one or more modules, sub programs, orportions of code). A computer program can be deployed to be executed onone computer or on multiple computers that are located at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification areperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output thereby tying the process to a particular machine(e.g., a machine programmed to perform the processes described herein).The processes and logic flows can also be performed by, and apparatuscan also be implemented as, special purpose logic circuitry, e.g., anFPGA (field programmable gate array) or an ASIC (application specificintegrated circuit).

Computer readable media suitable for storing computer programinstructions and data include all forms of non-volatile memory, mediaand memory devices, including by way of example semiconductor memorydevices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks(e.g., internal hard disks or removable disks); magneto optical disks;and CD ROM and DVD ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular embodiments of particularinventions. Certain features that are described in this specification inthe context of separate embodiments can also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment can also beimplemented in multiple embodiments separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Particular embodiments of the subject matter described in thisspecification have been described. Other embodiments are within thescope of the following claims. For example, the actions recited in theclaims can be performed in a different order and still achieve desirableresults, unless expressly noted otherwise. As one example, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In some implementations, multitasking and parallel processingmay be advantageous.

We claim:
 1. A method comprising: receiving, at a wide area network(WAN) adapter located at a premise, one or more WAN communications fromone or more networks, wherein the WAN adapter comprises at least a 6 GHzradio for providing a 6 GHz wireless backhaul for communication with agateway device with tri-band capability located at the premise;converting the one or more WAN communications to one or more 6 GHzwireless fidelity (Wi-Fi) signals for delivery to a 6 GHz gateway deviceradio of the gateway device over a 6 GHz wireless band provided by the 6GHz radio of the WAN adapter; outputting the one or more Wi-Fi signalsto the gateway device over the 6 GHz wireless band of the 6 GHz radio;and communicating with an access point over the 6 GHz wireless backhaul.2. The method of claim 1, wherein the one or more WAN communications arereceived at the WAN adapter from one or more WAN adapters, wherein theone or more WAN adapters are different from the WAN adapter.
 3. Themethod of claim 2, wherein the WAN adapter communicates with the one ormore WAN adapters via a wired connection between the WAN adapter and theone or more WAN adapters.
 4. The method of claim 1, wherein the WANadapter further comprises at least a 2.4 GHz radio and a 5 GHz radio. 5.The method of claim 1, wherein the WAN adapter receives the one or moreWAN communications from a client device or an extender facilitated bythe gateway device.
 6. The method of claim 1, wherein the WAN adapterprovides at least a 6 GHz wireless local area network and a 5 GHzwireless local area network.
 7. The method of claim 1, wherein the WANadapter operates as a mmWave to 6 GHz convertor.
 8. The method of claim1, wherein the WAN adapter comprises a removable interface module thatfacilitates the conversion of the one or more WAN communications to oneor more 6 GHz communications.
 9. A wide area network (WAN) adapter forreceiving one or more WAN communications, the WAN adapter comprising: aradio, wherein the radio receives one or more WAN communications fromone or more networks, and wherein the radio comprises at least a 6 GHzradio for providing a 6 GHz wireless backhaul for communication with agateway device with tri-band capability located at the premise; aninterface, wherein the interface converts the one or more WANcommunications to one or more wireless fidelity (Wi-Fi) signals fordelivery to a 6 GHz gateway device radio of the gateway device over a 6GHz wireless band provided by the 6 GHz radio of the WAN adapter; amemory storing one or more computer-readable instructions; and aprocessor configured to execute the one or more computer-readableinstructions to: output the one or more Wi-Fi signals to the gatewaydevice over the 6 GHz wireless band of the 6 GHz radio; and communicatewith an access point over the 6 GHz wireless backhaul.
 10. The WANadapter of claim 9, wherein the one or more WAN communications arereceived at the WAN adapter from one or more WAN adapters, wherein theone or more WAN adapters are different from the WAN adapter.
 11. The WANadapter of claim 10, wherein the processor is further configured toexecute the one or more computer-readable instructions to: communicatewith the one or more WAN adapters via a wired connection between the WANadapter and the one or more WAN adapters.
 12. The WAN adapter of claim9, wherein the radio further comprises at least a 2.4 GHz radio and a 5GHz radio.
 13. The WAN adapter of claim 9, wherein the process isfurther configured to execute the one or more computer-readableinstructions to: provide at least a 6 GHz wireless local area networkand a 5 GHz wireless local area network.
 14. One or more non-transitorycomputer readable media having instructions operable to cause one ormore processors to perform the operations comprising: receiving, at awide area network (WAN) adapter, one or more WAN communications from oneor more networks, wherein the WAN adapter comprises at least a 6 GHzradio for providing a 6 GHz wireless backhaul for communication with agateway device with tri-band capability located at the premise;converting the one or more WAN communications to one or more wirelessfidelity (Wi-Fi) signals for delivery to a 6 GHz gateway device radio ofthe gateway device over a 6 GHz wireless band provided by the 6 GHzradio of the WAN adapter; outputting the one or more Wi-Fi signals tothe gateway device over the 6 GHz wireless band of the 6 GHz radio; andcommunicating with an access point over the 6 GHz wireless backhaul. 15.The one or more non-transitory computer readable media of claim 14,wherein the one or more communications are received at the WAN adapterfrom one or more WAN adapters, wherein the one or more WAN adapters aredifferent from the WAN adapter.
 16. The one or more non-transitorycomputer readable media of claim 15, wherein the WAN adaptercommunicates with the one or more WAN adapters via a wired connectionbetween the WAN adapter and the one or more WAN adapters.
 17. The one ormore non-transitory computer readable media of claim 14, wherein the WANadapter further comprises at least a 2.4 GHz radio and a 5 GHz radio.18. The one or more non-transitory computer readable media of claim 14,wherein the WAN adapter provides at least a 6 GHz wireless local areanetwork and a 5 GHz wireless local area network.
 19. The one or morenon-transitory computer readable media of claim 14, wherein the WANadapter operates as a mmWave to 6 GHz convertor.
 20. The one or morenon-transitory computer readable media of claim 14, wherein the WANadapter comprises a removable interface module that facilitates theconversion of the one or more WAN communications to one or more 6 GHzcommunications.